Customized Search

ABSTRACT

Techniques are disclosed herein for providing a custom search engine. In one aspect, a first search query is received from a requestor. First search results contain search result items that match the first search query are obtained. A least one sub-query is generated from the first search results. The generating is based on rules for a particular custom search engine. Second search results that match the sub-query are then obtained. A search result set is formed from a corpus that includes the first search results and the second search results. The generating of the search result set is based on the rules for the particular custom search engine. The search result set is provided to the requestor. In one aspect an interface for designing a custom search engine is provided. The interface allows the designer to specify the layout of a search results page.

CLAIM OF PRIORITY

This application is a divisional application of U.S. patent applicationSer. No. 12/253,658, entitled “CUSTOMIZED SEARCH,” by Shafer et al.,filed Oct. 17, 2008, incorporated by reference herein in its entirety.

BACKGROUND

Through the use of the Internet, individuals have access to millions ofpages of information. However a significant drawback with using theInternet is that because there is so little organization to theInternet, at times it can be extremely difficult for users to locate theparticular “web pages” that contain the information that is of interestto them.

To address this problem, “search engines” index a large number of webpages and provide an interface that can be used to search the indexedinformation by entering certain words or phases to be queried. Indexesare conceptually similar to the normal indexes that are typically foundat the end of a book, in that both kinds of indexes comprise an orderedlist of information accompanied with the location of the information.

Although there are many popular Internet search engines, they aregenerally constructed using the same three common parts. First, eachsearch engine has at least one “spider” that “crawls” across theInternet to locate web pages around the world. Upon locating a web page,the spider stores the web page's Uniform Resource Locator (URL), andfollows any hyperlinks associated with the web page to locate other webpages. Second, each search engine contains an indexing mechanism thatindexes certain information about the web pages that were located by thespider. The indexing mechanism stores the index information in largedatabases that can typically hold an enormous amount of information.Third, each search engine provides a search tool that allows users tosearch the databases in order to locate specific web pages that containinformation that is of interest to them.

The search engine provides an interface that allows users to specifytheir search criteria and, after performing a search, an interface fordisplaying the search results. Typically, the search engine orders thesearch results prior to presenting the search results interface to theuser. The order usually takes the form of a “ranking”, where the webpage with the highest ranking is the web page considered most likely tosatisfy the interest reflected in the search criteria specified by theuser. The specific techniques for determining that ranking will varyfrom implementation to implementation.

Once the matching web pages have been determined, and the display orderof those web pages has been determined, the search engine sends to theuser that issued the search a “search results page” that presentsinformation about the matching web pages in the selected display order.Significantly, the search results page does not present to users thematching web pages themselves, but merely data that identifies thematching web pages. Typically, the number of web pages that match asearch is so large that the user is presented with a search results pagethat only displays information about the top N ranking web pages, whereN may be significantly smaller than the total number of matching webpages. The search results page typically includes a control that allowsthe user to retrieve information about the “next N” matching documents,in the event the first N matching web pages do not entirely satisfy theuser's interest.

Attempting to augment the search experience that a search engine canprovide requires significant development skill and substantialresources, which can provide barriers. For example, a small company thathas a web site might want to add some search capability to their website. Ideally, the search would involve the proprietary content of thecompany (e.g., inventory data), as well as content not owned by thecompany (e.g., web content). However, the while the small company hasrelevant proprietary content and domain expertise for a particulartopic, the small company does not have the capability to build thesearch experience. Moreover, the small company would prefer not to incurthe cost of hiring a consultant to build the search experience.

SUMMARY

Techniques are disclosed herein to make use of the infrastructure ofexisting search engines to support other search experiences rather thanjust the search engine's singular search experience. By creating aplatform around these infrastructures, non-developers can feed in theirproprietary content and create a custom search engine around theirproprietary content that also leverages services within the searchplatform to provide news, web content, related queries, etc. Because theproprietary content may be structured, the platform supports queryingstructured data. The content is kept proprietary and is not surfacedanywhere else but in the owner's custom search engine (unless authorizedby the owner). The designer of the custom search engine has full controlover the layout of the search results page, how search result links aredisplayed, how structured results are shown, and where advertisements(if any) are placed.

In one implementation, information is received from a requestor. Contentthat contain items is determined based on the information. A least onesub-query is generated from the content. The generating is based onrules for a particular custom search engine. Search results that matchthe at least one sub-query are then obtained. A search result set isformed from the items in the content and the search results. Thegenerating of the search result set is based on the rules for theparticular custom search engine. The search result set is then providedto the requestor.

In one implementation, the information from the requestor is a searchquery. In one implementation, the information pertains to the requestorin some manner. For example, the information may identify the requestor,the requestor's location, etc. The information from the requestor mayinclude both a search query and information that pertains to therequestor.

Another aspect is a method for providing an interface for a designer todesign a custom search engine. In this aspect, an interface for adesigner to design a custom search engine is provided. The followinginformation is received in the interface: a) either first content to besearched or identification of first content to be searched by the customsearch engine; b) information that specifies how to construct asub-query from first search results that are returned when the firstcontent is searched by the custom search engine; c) either secondcontent to be searched or identification of second content to besearched using the sub-query, second search results are returned whenthe second content is searched using the sub-query; and d) informationthat specifies how to generate final search results from the firstsearch results and the second search results. The information that isreceived in the interface is stored, and the stored information isassociated with the custom search engine.

Another aspect is a system comprising a processor and a computer storagemedium coupled to the processor. The computer storage medium hasinstructions, which when executed on the processor implement a methodcomprising the following. A first search query is received from arequestor. Metadata that identifies a particular custom search engine isreceived from the requestor. Stored configuration information for theparticular custom search engine that is identified by the metadata isaccessed. Based on the configuration information, a first corpus tosearch is determined. The first corpus is searched using the firstsearch query to obtain first search results that match the first searchquery. One or more sub-queries are generated from search results itemsin the first search results. The one or more sub-queries are generatedbased on the configuration information. Based on the configurationinformation, a second corpus to search is determined. The second corpusis searched using the at least one sub-query to obtain second searchresults that match the one or more sub-queries. A search result set isgenerated from a corpus that includes the first search results and thesecond search results. Generating the search result set is based on theconfiguration information. The search result set is provided to therequestor.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an overview of one embodiment of a system forproviding a custom search engine.

FIG. 2 depicts one embodiment of a search results page.

FIG. 3 is one embodiment of a process of providing a custom searchengine.

FIG. 4 shows one embodiment of a main web page for a designer that hascreated several custom search engines.

FIG. 5 is a flowchart of one embodiment of a process of constructing acustom search engine.

FIG. 6 is a flowchart depicting one embodiment of a process of receivingcontent and configuration information in an interface for designing acustom search engine.

FIG. 7A is one embodiment of a configuration tool that allows thedesigner to upload or register their content with a server.

FIG. 7B is one embodiment of a configuration tool that allows thedesigner to provide configuration information for a custom searchengine.

FIG. 8A depicts one embodiment of a drag and drop interface for creatinga custom search engine.

FIG. 8B shows one embodiment of a configuration tool to customizecontent to be searched.

FIG. 8C depicts one embodiment of a configuration tool that allows adesigner to customize how the content is laid out in the search resultspage.

FIG. 8D is one embodiment of an interface to configure the “InternetSearch” component from the “engine drag-n-drop” page from FIG. 8C.

FIG. 9A is flowchart illustrating one embodiment of providing code to adesigner to help publish a custom search engine.

FIG. 9B is flowchart illustrating one embodiment of providing code to adesigner to help the designer embed a custom search engine on their website.

FIG. 10 is a one embodiment of an interface for providing code to adesigner to help the designer publish a custom search engine.

FIG. 11 is a block diagram for an embodiment of a computing environmentfor implementing the present technology.

DETAILED DESCRIPTION

FIG. 1 illustrates an overview of one embodiment of a system forproviding a custom search engine. The system allows designers to build acustom search engine that combines their own proprietary data such aselectronic files that describe a store's inventory with third partyinformation such as product reviews. The designer is allowed to definewhat information from their content and what third party informationshould appear on the search results page. Moreover, the designer isallowed to specify how the information should be arranged on the searchresults page.

The following examples will illustrate how the system can be used tocreate a custom search engine. A shoe store owner has a web site thatcustomers visit to learn what shoes and related merchandise the storehas for sale. However, the web site is somewhat limited in scope due tothe time, cost, and expertise required to construct web sites. The shoestore has a database describing the inventory of shoes and related itemsfor sale. This database stores the information in a structured, or atleast, semi-structured manner. For example, the database entries havefields for item description, sizes available, price, etc.

The shoe store owner may desire that the web site augments the limitedinformation available on the web site with product reviews, tips on shoeselection, trail guides, etc. Such information may be readily availableon the Internet or another source. Moreover, the store owner desiresthat customers have an easy way to search for shoe related informationwhile the customer is on the shoe store's web site. However, the shoestore may not have any expertise in constructing web sites and may wishto avoid the expense of hiring a consultant to expand the web site.Thus, although there is readily available third party information thatmight be used to enhance the customers' experience when visiting theshoe store web site, linking the third party information with the shoeinventory information presents problems. The system of FIG. 1 allows theshoe store to easily link the third party information with the shoeinventory data. Specifically, the system allows the shoe store to createa custom search engine in which a customer can enter a search query onthe shoe store web site and obtain search results that are a combinationof the shoe store inventory and other information such as productreviews, tips on buying shoes etc.

As another example, a video rental/sale store owner has structuredcontent such as movie titles, ratings (e.g., G, PG, R, etc.), genre,plot descriptions, rental price, sale price, etc. As with the shoe storeexample, this information is in electronic form such as files or adatabase. The video store owner does not have, but knows where tolocate, other information such as in-depth movie reviews, movietrailers, movie posters, and discussion forums on movie related topics.The system allows the video store to leverage the store's structuredcontent with the other information by allowing for creation of a customsearch engine. In this example, when a customer enters a search queryfor a movie on the video store web site, the custom search enginereturns a search results page in which each entry lists the informationfrom the store's content with a review from a third party web site, aposter or trailer, and several URLs that link to discussions about themovie.

As still another example, a private individual who is a wine enthusiastwishes to share the designer's enthusiasm for certain wines. Thedesigner has a list of their favorite wines. However, this designer doesnot have a web site. In this example, the designer might wish to add acustom wine search engine to a publically available web site. Thus,others can use the custom wine search engine. This custom search enginemight function as follows. If the search “cabernet” is entered, the winelist is searched for cabernets to produce initial search results. Then,certain web sites (specified by the wine enthusiast and configured intothe custom search engine) are searched for reviews of each of thecabernets. The final search results contain a link to reviews for eachof the cabernets.

Note that it is not required that the custom search is kicked off withan initial search based on a search query. For example, the experiencecan start by determining some set of initial content (rather than searchresults) based on information that it is pertinent to a user. Theinformation could be a user ID, e-mail address, etc. As a specificexample, when John Smith logs in he is identified and a list of stocksis obtained from proprietary content associated with John Smith. Then,one or more searches are performed to obtain search results for one ormore of the stocks on the list. For example, the latest reviews of eachstock from a particular analyst are obtained, the latest stock pricesare obtained, news for each stocked is searched for, etc.

Further note that the above examples illustrate possible uses of thesystem. However, as will be clear from the discussion herein, the systemallows for many other types of custom search engines. As the example ofthe wine enthusiast illustrates, the system is not limited to retailapplications. Further, while the above examples are of the custom searchengine designer providing their own content to be searched (andaugmented with another search), there is no requirement that thedesigner provide their own content to be searched by the custom searchengine.

FIG. 1 depicts a web page 102 having a search box 106 that serves as anentry point to a custom search engine. Web page 102 is, for example, aweb page on a web site for an online shoe retailer. The web page content108 could be any content on the web site. In one embodiment, the server110 provides code (e.g., an HTML snippet) to a custom search enginedesigner when the designer sets up the custom search engine. Thedesigner may insert the code in a suitable location on the web page 102.Thus, the designer is not required to know how to write HTML code inorder to establish a starting point for the custom search engine.Providing code to the designer is not a requirement. Note that it is notrequired that the entry point to the custom search engine be the searchbox 106. In other words, it is not required that a search query issubmitted at the entry point. In one implementation, some userinformation such as a user ID, e-mail address, name, location, etc. issubmitted at the entry point. In some implementations, both a searchquery and user information is submitted.

FIG. 1 also depicts a search results page 104 that is specially adaptedfor the custom search engine. The search results page 104 has embeddedJavaScript that automatically forwards a search query that is enteredinto search box 106 on to the server 110 along with metadata thatidentifies the custom search engine. The metadata may also containinformation that pertains to the user that submitted the search query,as discussed above. As also discussed above, it is not a requirementthat a search query be submitted. In one embodiment, the server 110provides the JavaScript to the designer when the designer establishesthe custom search engine. The designer inserts the JavaScript into anappropriate location on the results page 104. The JavaScript alsoinserts the search results 132 into the proper place on the searchresults page 104. Thus, the designer is not required to know how towrite JavaScript or another coding language.

Both the web page 102 and the search results page 104 may be rendered ona client, which is a computer software application that executes on acomputing platform, such as a desktop or laptop computer, to communicatewith a server computer software application. The client facilitates aprocess in which an end user, such as a person requesting a search forinformation, communicates with the web site that offers the customsearch engine (e.g., shoe retailer). The client may be a conventionalweb browser that facilitates communication over a network, such as theInternet.

In one implementation, the custom search engine performs a first searchof initial content 140 with the search query entered in search box 106.The custom search engine may also use the user information to helpperform the search. In one implementation, the custom search enginedetermines initial content based on user information without performinga search based on a search query. For example, a list of Jim Smith'sstocks is returned.

In one aspect, the initial content 140 is content provided by the customsearch engine designer (herein “designer content”). As examples, thedesigner content may be the shoe inventory of web site that marketshoes, movies and video games for sale or rent by an online retailer, ora wine list supplied by a wine enthusiast. In one embodiment, the server110 provides an interface for the designer to supply the designercontent when setting up the custom search engine. The designer contentmay be structured, or at least semi-structured. For example, thedesigner content may have certain fields such as a title field, a pricefield, etc. Note that the designer content is specific to the customsearch engine in this example.

The server 110 has access to additional content 150. In someembodiments, the additional content 150 is searched to augment theresults of searching the initial content 140. The additional content 150is not limited to any particular content. For example, the additionalcontent 150 might be any content available through an Internet search,or it could be limited to specific URLs (which may or may not beavailable in a typical Internet search). In some embodiments, theadditional content is a specific “service” provided by a search engine.For example, some search engines have different services that search fornews, images, sports, etc.

The server 110 has access to configuration data 112 that defines howsearch queries should be processed and how search results should beconstructed by each custom search engine. The metadata sent by theJavaScript is used to identify what configuration information to use forthe custom search engine. The configuration data for a particular customsearch engine is based on information provided by the designer duringthe process of setting up the custom search engine.

In one aspect, the configuration information defines what initialcontent 140 should be searched using the initial query. The initialresults 122 are what are generated from the processing of the initialquery, the user information, or both. For example, initial searchresults may be returned from the initial search query with or withoutbasing the search on user information. Note that the initial results 122may be based entirely on user information. In one implementation, theinitial search query is used to search designer content that is providedwhen the custom search engine was established. However, the initialsearch can be of any content. Thus, it is not a requirement that theinitial results 122 are generated from searching designer content.

The query processing module 120 is able to form sub-queries from theinitial results 122 using rules in the configuration information for thecustom search engine. The query processing module 120 also determineswhat content (or corpus) should be searched using the sub-queries. Thisdetermination is made based on the configuration information for theparticular custom search engine. The additional search results 124 arethe results from executing the sub-queries. Together the initial results122 and the additional results 124 form a total result set 126.

The result processing module 130 generates final results 132 from thetotal result set 126. The result processing module 130 inputs theconfiguration information for the custom search engine to determine howto generate the final results 132 for the particular custom searchengine.

FIG. 2 depicts one embodiment of a portion of a search result page 104.The results are for a search “xbox” that was entered into the search box106. This search query is re-displayed in the search box 202 of thesearch results page 104. In this example, the final search results are acombination of the initial results 122 and additional search results124. The final search results are organized in a repeating pattern of atitle of a movie or video game 204, a description of the movie/videogame 206, an image 208, the word “reviews” 210, and links to reviews212. The title 204, description 206, and image 208 are taken from theinitial results 122. The links to reviews 212 are taken from theadditional search results 124.

The title 204 may be taken from a title field of structured designercontent, the description 206 from a description field, and the image 208from an image in the designer content. Note that it is not required thatthe initial results 122 be structured results. In this example, theinitial results 122 were derived from searching designer content for anonline movie/video game retailer. Result items 204 a, 206 a, and 208 aare derived from a record in the designer content for the video game“Hail to the Chimp”. The data used to create the “Hail to the Chimp-Xbox360” hyperlink 204 a, the thumbnail image 208 a, and the gamedescription 206 a all come from corresponding fields in that record.

In this example, the corpus that was searched to produce the additionalsearch results 124 was three web sites that are specified when thecustom search engine was established. Note that the search against thisadditional content 150 was driven not by the original “xbox” query, butrather by the name field from the “Hail to the Chimp” record. Similarly,for the next result item, the search query used to search the additionalcontent 150 to generate review links 212 b is derived from the title“NCAA Football 09-Xbox 360” 204 b (which is based on a title field forthe corresponding record in the designer content). This shows oneexample of search results that are a combination of designer structuredcontent uploaded to the server 110 by the designer and web contentobtained on-the-fly.

FIG. 3 is one embodiment of a process 300 of providing a custom searchengine. Process 300 may be implemented by executing instructions, whichare stored on a computer storage medium, on a processor. In oneembodiment, the server 110 performs process 300. Process 300 will bediscussed with reference to the system of FIG. 1; however, process 300is not limited to the system of FIG. 1. Process 300 will be discussedusing an example in which the custom search engine is for a web sitethat sells movies, video games, and the like. Process 300 will also bediscussed with reference to FIG. 2, which depicts an example resultspage 104.

In step 302, the server 110 receives initial information and metadataidentifying the custom search engine. The initial information mayinclude an initial search query and/or user information. In the presentexample, the user enters the query “xbox” in the search box 106 on theweb site of the online movie and video game retailer. This causes aframework for the search results page 104 to be loaded on the client ofthe user. The framework for the search results page 104 has embeddedJavaScript that sends the initial search query to the server 110, alongwith metadata that identifies the particular custom search engine. Aspreviously indicated, the metadata may also include user information.The metadata is used to identify the correct configuration informationfor the custom search engine. In step 304, stored configurationinformation for the custom search engine is accessed based on themetadata.

In step 306, a determination is made as to what content to search forthe custom search engine identified by the metadata. In one embodiment,the query processing module 120 identifies what portion of the designercontent to search based on the configuration data. In the presentexample, the designer content provided by the movie/video game retaileris identified in the configuration data. However, the initial content tobe searched is not limited to designer content. For example, the initialcontent to be searched could be the entire web, specified URLs, orservices (e.g., news, weather, sports, finances). Note that anycombination of these example sources can be searched.

In step 308, first results are produced based on the information fromstep 302. For example, the content identified in step 304 is searched toproduce initial results 122 that match the initial search query. Asanother example, a list of a particular user's stocks is produced basedon user information. Referring to FIG. 1, in one implementation, thequery processing module 120 uses the initial search query to searchspecifically identified portions of the initial content. A set ofinitial results 122 are generated as a result of the search. In someembodiments, the initial results 122 are formed from a search ofstructured content, and hence reflect that structure themselves. Forexample, FIG. 2 shows final search results that are formed fromstructured content. Note that the first results 122 might be sub-dividedinto different categories based on what content was searched. Forexample, there could be a category of results based on searching weatherand another category of results based on searching news, etc.

In step 310, a determination is made as to what content to search usingthe sub-queries. This determination is made based on rules in theconfiguration information for the custom search engine. As an example,the designer that created the custom search engine identifies one ormore URLs of web sites that provide movie and or video game reviews tobe searched. In this example, the URLs are known to the designer, butnot owned by the designer. However, the content to be searched could becontent provided by the designer. As previously discussed, there is nolimit to what might be searched with the sub-queries. In some cases, thedesigner content might be searched with the sub-queries. Note that thecontent could include many different sources, such as a news source, atravel package source, etc.

In step 312, one or more sub-queries are generated from the initialresults 122. Each sub-query is generated based on rules in theconfiguration information. As an example, the rules indicate that thesub-query should take the title from the title field of each searchresult item in the initial results 122 and add on the word “review.” Forexample, for the search result item “hail to the chimp-Xbox 360”, thesearch “hail to the chimp-Xbox 360 review” is formed. Some terms couldbe removed from the search result item to form the sub-query. Forexample, “Xbox 360” might be removed. In some cases, the sub-query isformed exactly from the search result item.

Note that in this example, the initial results 122 are based onsearching structured content, and thus it is known that a movie or videogame title is being extracted from the title field. However, aspreviously indicated it is not an absolute requirement that the contentthat is searched be structured. Therefore, it might not be known whetherthe data in the fields of the search result items are titles orsomething else.

As previously discussed, the initial results can split into differentcategories. For example, for a travel search engine, the content thatwas searched could be travel packages and a news service. Thus, theinitial results 122 would contain a travel packages search results andnews search results (in this example each based on the initial query).Sub-queries can then be formed from the travel package search results toquery “second-level” content in order to show the weather for thelocation of each travel package as well as web results for recommendedrestaurants. The content sources for weather and restaurants may beentirely different, and may also use different fields from thetravel-package results to create their sub-query. However, it may bethat no sub-queries are formed from the news results. Thus, note that 0,1, or many types of sub-queries can be formed for each type of searchresult.

The actual number of sub-queries that are formed can be limited to avoidhaving to perform too many searches. For example, the configurationinformation can specify that the initial results 122 should only contain10 items. Therefore, in the present example the initial results 122would have 10 items, each with a title of a movie or video game (andassociated description and image). Thus, 10 different sub-queries wouldbe formed to search for reviews for 10 different movies (or videogames).

In step 314, the content identified in step 310 is searched to produceadditional search results 124 that match the sub-queries. As an example,for each video game title in the initial results, the additional searchresults contain links to specific web pages that review that video game.FIG. 2 depicts several links 212 below the word “review.” The threelinks 212 a are taken from one or more sub-queries based on the titlefield, “Hail to the Chimp.”

In step 316, final search results 132 are generated. The final searchresults 132 are based on the combined initial results 122 and theadditional search results 124. In the example of FIG. 2, the finalresults contain results from both the initial results 122 and theadditional search results 124. However, note that the final searchresults 132 might contain only the initial results 122, only theadditional search results 124, or a combination of both. As one example,the additional search results 124 might be used to determine whichinitial results 122 should be included in the final search results 132.For example, first a search of movie reviews is performed. The querymight be an actor's name. Then, a search of the online retailer's movieinventory is made using sub-queries that are based on movie titles inthe movie reviews. Only reviews for movies that are in stock are shownin the final search results 132. Note that this not only illustratesthat the additional search results 124 do not need to be displayed inthe final search results 132 (although they are used to determined whatis displayed in this example), but this also illustrates that the secondcontent to be searched could be designer content.

In step 318, the final search results 132 are provided to the requestor.For example, HTML representing the final search results 132 is sent backto the user's browser. The HTML is received by the JavaScript, whichinjects it into the results page 104. Details of how a designer canconfigure the results page layout are discussed below. To the user, theresults appear as though they came seamlessly from the owner's web-site.

FIG. 4 shows one embodiment of a main web page 400 for a designer thathas created several custom search engines. In one implementation, server110 makes web page 400 available. The web page 400 has links to each ofthe custom search engines 412. The designer can access their customsearch engines by following one of the links 412. The designer canchoose to edit or delete any of the custom search engines or to create anew custom search engines. If the designer selects the create new searchengine link 414, a web page such as the one depicted in FIG. 7B isaccessed to allow the designer to configure a search engine. The webpage 400 also has links to content 416 that the designer has suppliedfor use by the custom search engines. The web page also has a “definenew content” link 418 that allows the designer to define new content. Ifthe designer selects link 418, then a web page such as the one depictedin FIG. 7A is accessed. Note that other interfaces for configuringsearch engines and providing content are contemplated than theinterfaces in FIGS. 7A and 7B. In some embodiments, the designer sharestheir custom search engines by, for example, placing them on the server110.

FIG. 5 is a flowchart of one embodiment of a process 500 of constructinga custom search engine. Process 500 may be implemented by executinginstructions, which are stored on a computer storage medium, on aprocessor. In one embodiment, the server 110 performs process 500. Thesteps are described in a particular order as a matter of convenience.Note that the steps can be performed in a different order.

In step 502, an interface to create a custom search engine is provided.FIGS. 7A and 7B depict one embodiment of such an interface. FIGS. 8A-8Edepict another embodiment of an interface to create a custom searchengine that uses a “drag and drop” approach.

In step 504, content and configuration information for the custom searchengine are received in the interface. The discussion of process 600 ofFIG. 6 below provides further details of one embodiment of receiving thecontent and the configuration information.

In step 506, the content and configuration information for the customsearch engine is stored. For example, server 110 stores designer contentprovided by the designer in the initial content 140. The server 110might alternatively store an identifier for the content such as a URL.Note that the identifier of the content might be stored elsewhere, suchas in the configuration data 122. The server 110 stores theconfiguration information for the custom search engine in theconfiguration data 112.

In step 508, the configuration information is associated with the customsearch engine such that the configuration information can be retrievedwhen a search is performed using the custom search engine. Thus, theconfiguration information can later be identified when the JavaScriptassociated with the search results page 104 sends metadata thatidentifies the custom search engine.

FIG. 6 is a flowchart depicting one embodiment of a process 600 ofreceiving content and configuration information in an interface fordesigning a custom search engine. Process 600 may be implemented byexecuting instructions, which are stored on a computer storage medium,on a processor. In one embodiment, the server 110 performs process 600.Process 600 is one technique for implementing step 504 of process 500.

In step 601, designer content is uploaded to (or alternativelyregistered with) the server 110. The content can be uploaded to theserver 100 (or other server) in a variety of different techniques suchas an HTTP file upload using a web browser, RSS feeds. The content couldhave a variety of data formats including, but not limited to, delimitedfiles, Excel files and XML. Rather that providing the content itself,the designer may simply identify the content. For example, the designercould supply root URLs. In this case, the server 110 performs a crawl ofweb sites associated with the root URLs and generates an index. Notethat the URLs supplied by the designer need not be otherwisediscoverable by an ordinary server crawler. Also, if those URLS areblocked (e.g., by a robots.txt file), then the designer may need toauthorize the server crawler by adding it to the list of allowedcrawlers.

FIG. 7A is one embodiment of a configuration tool 700 that allows thedesigner to upload or register their content with the server 110. In oneimplementation, server 110 makes configuration tool 700 available fordesigners through a web page. This configuration tool 700 can be used instep 601 of process 600. In this example, the designer is configuring asearch engine named “Video Games.” Specifically, the designer isconfiguring details of content to be searched when using the customsearch engine. The designer has entered a short description of thecontent in the description box 702. In this embodiment, the designer isallowed to specify a “root or feed” URL in box 704 to identify thecontent to be searched. If the designer specifies a root URL, the server110 will crawl the web site of the URL to obtain the content. If thedesigner specifies a feed URL, the server 110 pulls the file from theURL. The designer is allowed to browse their computer system anddirectly upload a file by entering a file path name into box 706. Thedesigner can also cut and paste content such as an XML file into theinline text box 708. For example, the designer can enter XML, contentabout video games into the text box 708. This content might be couldrepresent a designer's wish-list, their personal collection of videogames, inventory of a video-game store, etc. Thus, the content mayrepresent the designer's proprietary data and may have some structuresuch as name, description, price, ticker symbol, etc.

In step 602, the content to be used for the initial search is identifiedby the designer. FIG. 7B is one embodiment of a configuration tool 750for providing configuration information. In one implementation, server110 makes configuration tool 750 available for designers through a webpage. In FIG. 7B, the designer is configuring the same search engine“video games” that the designer uploaded content for in the interface ofFIG. 7A. The user has entered a description of the custom search enginein box 703. This configuration tool 750 can be used to identify thecontent for the initial search. Specifically, if the designer selectsthe arrowhead 760, a drop down menu appears below content box 754,allowing the designer to select what content of theirs should be used.Specifically, this menu contains a list of the content under the “mycontent” heading of the web page of FIG. 4. In this case, the designerhas selected the “games” content. Fields 756-760 of this configurationtool 750 will be discussed later in process 600.

In step 604, instructions for how the content identified in step 602should be searched is received. In one aspect, the default is that anytext-based fields will be used for free-text search, and numeric fieldswill be used for parametric search. The designer may refine which fieldsof the content are to be used, and in the case of parametric search,what similar words could be used to refer to a given field. For example,to support both the queries “8 megapixel digital camera” and “8MPdigital camera”, the designer might indicate that the “megapixels” fieldin the data can be referred to by users as “megapixel” or “MP”. However,note that the server 110 may already have a large variety of synonymsbuilt-in. Thus, the designer-provided synonyms serves as a backstop.Some attributes such as “price” will also need to be explicitlyidentified to support queries of the form “digital camera around $400”.

In step 606, the designer specifies how content that matches the searchquery should be formatted. For example, the designer specifies whichfields from the content should be presented as part of each searchresult. As a specific example, the designer specifies that the titlefield should be included in the search results. In one embodiment, thedesigner specifies the layout of the results page. For example, thedesigner specifies exactly where the movie title, movie description, andmovie trailer should appear.

In step 608, the designer identifies additional content to be searched.In one implementation, the designer is allowed to select from a varietyof services ranging from web-results, news, image, video, instantanswers, etc. Note that the service is in effect tailored for the customsearch engine by selection of the sub-queries (e.g. product name) andhow many results to show. Also note that a selected portion of theservice might be searched rather than the entire service. For example,web-search could be customized to restrict or prefer certain sites. Inone aspect, advanced query operators such as “prefer:” and “location:”are used. A service that provides “instant answers” could be customizedto allow only desired answers, such as the “weather instant answers” ina vacation-package custom search engine or a “product sentiment answer”in a custom search engine related to product shopping. Referring againto the configuration tool 750 of FIG. 7B, the designer may specify oneor more URLs in the URL box 756 to identify the additional content. Thisembodiment also has a “suggest URL” button 762, which triggers afunction that suggests URLs to the designer.

In step 610, the designer provides any special query terms. Referringagain to FIG. 7B, the query term box 758 allows the designer to specifyspecial query terms. In one aspect, the query terms are used toinfluence the ranking of the search results. For example, search resultsthat have the query term receive a boost in the ranking. In anotheraspect, the query terms are used to augment the sub-queries.

In step 612, the designer indicates whether or not they wish to haveadvertisements on the results page. If advertising is enabled, thedesigner may automatically benefit from advertisement revenue sharing.In some embodiments, the designer can customize what terms are used totrigger advertisements. In some embodiments, the designer can customizewhat types of advertisements and advertisers should be allowed.Referring again to FIG. 7B, the interface has an “advertising” check box760 for the designer to select.

In step 614, the designer specifies the layout of the final searchresults 132. FIGS. 8A-8D depicts configuration tools that allow adesigner to configure a search engine and identify content to besearched using a drag and drop approach. The drag and drop approachprovides a very convenient easy way for the designer to arrange thelayout of the search results page 104. In one embodiment, the designeris allowed to select from a set of pre-defined templates for the layoutof the search results 132.

FIG. 8A depicts one embodiment of a search engine drag and dropconfiguration tool 800 for creating a custom search engine. In oneimplementation, server 110 makes configuration tool 800 available todesigners through a web page. Designers are shown a palette 802 ofavailable content on the left side and the current layout 804 of thecustom search application on the right. More specifically, the layout804 drives how the search results page 104 will appear. Designers candrag content from the palette 802 and drop it onto their applicationlayout 804. This could be Internet content such as Web, News, Imageresults, custom/proprietary content registered with the server 110,advertisements, content from built-in services such as MSN Shopping,etc. Configuration tool 800 also lets the designers configure items suchas where the search box 805 should go on the results page 104 and pagenumbers 808 (for jumping to the next page of search results).

Many of components that designers drag onto the layout 804 can beconfigured, such as how many search results to show and what specificcontent should be searched. Many components in the layout 804 can havetheir own sub-layout specified. For example, the layout of the searchresults 806 can be configured by the configuration tool 840 of FIG. 8C.Thus, the designer can configure how the various items in the searchresults should be rendered on the search results page 104 (e.g. imagethumbnail first, then title with hyperlink, then description, etc.).

FIG. 8B shows one embodiment of a configuration tool 820 forcustomizations related to the content that is to be searched first bythe custom search engine. In one implementation, server 110 makesconfiguration tool 820 available to designers through a web page. Inthis example, the designer specifies what content to search first byselecting the arrowhead 760 to cause a drop down menu to be displayed(drop down menu not depicted). The designer has selected the gamescontent, which appears in the content box 826. By entering the value 10in the number of results box 822, the designer has specified that 10search result items from the game content are to be returned in thefinal search results 132. The designer may also configure additionalquery terms by entering them into the query augmentation box 824. In oneaspect, the query augmentation is used to add a search term to theinitial query entered in search box 106. In another aspect, the queryaugmentation is used to influence rankings of the initial results byboosting the ranking of results that include the term in the queryaugmentation.

FIG. 8C depicts one embodiment of a layout configuration tool 840 thatallows a designer to customize how the final search results 132 arearranged. In one implementation, server 110 makes layout configurationtool 840 available to the designer through a web page. Thisconfiguration tool 840 allows the designer to configure the layout ofthe results for the “search results” 806 component of FIG. 8A. Thelayout configuration tool 840 of FIG. 8C is similar to the mainconfiguration tool 800 of FIG. 8A in that the designer can drag and dropvarious components from the left palette 842 onto the search resultslayout 806.

Note that the search results layout 806 is reflected in the arrangementof FIG. 2. In the example, the designer has placed a hyperlink 844 ontop. The hyperlink component 844 may in turn be configured to use Titleand URL fields from the games structured content. The designer hasplaced image component 852 below the hyperlink component 844. This imagecomponent may be configured to use a thumbnail-url field in the gamesstructured content. The general field component 848 is for showing theraw description field from the games content. The designer can entertheir own text in the advanced text component 850. For example, the“review” text in FIG. 2 can be generated from the advanced text box 850.The designer has dragged and dropped an “Internet Search” component 852near the bottom. This will cause the additional search results to bedisplayed in that location. Note that this entire layout 806 is used torender a single result. For example, in FIG. 2 the layout corresponds toresult items 204 a, 206 a, 208 a, 210, and 212 a. Because the customcontent was configured to show up to 10 results, this layout will berepeated up to 10 times (possibly on different result pages).

FIG. 8D is one embodiment of a configuration tool 860 to configure the“Internet Search” component 852 from the “search result drag-n-drop”tool 840 from FIG. 8C. In one implementation, server 110 makesconfiguration tool 860 available to the designer through a web page.Note that this tool 860 is used to configure the additional search thatis based on the sub-queries. The designer is allowed to specify how manyadditional search results to show by entering a value in box 862. Theconfiguration tool 860 also shows that the designer has indicated thatfor each result in the initial results 122, web content from the threesites should be shown. In this example, those are gamespot.com, ign.comand teamxbox.com. This corresponds to having three links 212 a toreviews in FIG. 2.

The designer is allowed to specify what type of content to search in box868. In this example, the designer has selected a web search. Thedesigner is allowed to restrict the search to specified sites byclicking on the “add a site” button 870, which will bring up a URL box878 for the designer to enter a URL. The page 860 also lets the designerspecify any additional query terms for the search of the additionalcontent 150 in box 864. In one aspect the additional query terms areused to influence the ranking of the search results. In another aspect,the additional query terms are used to augment one or more of thesub-queries.

Note that in this example, a first component (the search resultcomponent 806) “contains” a second component (the Internet searchcomponent 852). Anytime a component (“child”) is added to the layout ofanother component, fields from the containing component can be used todrive the search in the child component. Thus, if the Internet searchcomponent 852 were to contain a child component, then fields from theInternet search component 852 could be used to drive a search of contentassociated with the child component. As an example, the first componentcould relate to a search of designer content for movies, the secondcomponent could relate to a search for movie reviews (the sub-queriesare based on the movie titles), and the third component could relate toa search for evaluations of the movie reviews (the sub-queries are basedon the movie reviewers). The result page could appear similar to that ofFIG. 2 with the augmentation of stars next to each movie review link 212to indicate the evaluation of the movie reviewer.

FIG. 9A is flowchart illustrating one embodiment of a process 900 forproviding code to a designer to help the designer publish a customsearch engine. Process 900 may be implemented by executing instructions,which are stored on a computer storage medium, on a processor. In oneembodiment, the server 110 performs process 900. In one embodiment, theinterface of FIG. 10 is used in process 900; however, process 900 is notlimited to that interface. In step 902, the designer identifies thecustom search engine that is to be published. As an example, the server110 provides the designer with an interface that allows the user toinput the name of the custom search engine. The user might select thename from a list of custom search engines (such as depicted in FIG. 4)or enter the name in a text box.

In step 904, the user provides some metadata that is related to theplatform in which the custom search engine is to be published. Theplatform may be the designers's own web site or a third party platform.For example, the designer may wish to publish their custom search engineto a social networking web site. The metadata may include, but is notlimited to, a URL and an application identifier. FIG. 10 depicts oneembodiment of an interface 1000 to enter the metadata. However, adifferent interface can be used.

In step 906, code is generated that allows the custom search engine tobe published to the specified platform. For example, the code is capableof creating a placeholder in the search results page 104 for the finalsearch results 132. The code may also be capable of communicating theinitial search query to the server 110. Further, the code may be able toobtain the final search results 132 from the server 110. Portions ofthis code may be HTML, JavaScript, or FBML (Facebook Markup Language),but is not so limited.

FIG. 9B is flowchart illustrating one embodiment of a process 940 forproviding code to a designer to help the designer add an entry point toa custom search engine to their web site. Process 940 is one techniqueof publishing a custom search engine as described in FIG. 9A. Process940 may be implemented by executing instructions, which are stored on acomputer storage medium, on a processor. In one embodiment, the server110 performs process 940. In step 942, an interface that allows adesigner to specify how to embed their custom search engine into theirown website is provided. FIG. 10 depicts one embodiment of an interface1000 to enter the information. In one implementation, server 110 makesinterface 1000 available to the designer through a web page.

In step 944, the designer specifies a search results URL in the resultURL box 1002. Step 944 is one technique for implementing step 904 ofprocess 900. The designer then clicks the generate HTML button 1008,which causes the server 110 to automatically generated code, in step946. The code (e.g., HTML) is used to create a search box 106. The HTMLis customized to expose the search engine the designer just created andconsists of static HTML for the search box 106. In FIG. 10, the server110 provides HTML in text box 1004 next to the “search HTML”. This“Search HTML” snippet can be used to render a simple search box 106anywhere on the target website. If a query is entered by a user into theprovided search box 106, the user will be taken to the results page 104.That is, the results page 104 is loaded in the client browser on theuser's computer.

In step 948, additional code is generated. The additional code mayinclude JavaScript that is able to automatically forward the initialsearch query to the server 110. The additional code may also be used tocreate a placeholder in the search results page 104 where the searchresults 132 will be displayed. This code generation step also occurs inresponse to the user clicking the create HTML button 1008, although adifferent button could be used. The text box 1006 next to the ResultHTML is where the server 110 provides a code snippet that the designermay embed in the search results page 104. This snippet is capable ofassisting in the rendering of the framework for the search results page104 that is loaded in the client after the user submits the initialquery and prior to the final search results 132 being received, as wellas forwarding the initial search query to the server 110. Steps 946 and948 are one technique for implementing step 906 of process 900.

The technology herein may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures and so forth that performparticular tasks or implement particular abstract data types. Thetechnology herein may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network. In a distributed computingenvironment, program modules may be located in both local and remotecomputer storage media including memory storage devices.

The technology described herein is operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of well known computing systems, environments,and/or configurations that may be suitable for use with the technologyherein include, but are not limited to, personal computers, servercomputers, hand-held or laptop devices, mobile phones or devices,multiprocessor systems, microprocessor-based systems, set top boxes,programmable consumer electronics, network PCs, minicomputers, mainframecomputers, distributed computing environments that include any of theabove systems or devices, and the like.

FIG. 11 depicts an example computer system 1100 that may serve as aplatform for embodiments of the present invention. The server 110 may beimplemented with such a computer platform. In its most basicconfiguration, the computer 1100 typically includes a processing unit1102 and memory 1104. Depending on the exact configuration and type ofcomputing device, memory 1104 may be volatile (such as RAM),non-volatile (such as ROM, flash memory, etc.) or some combination ofthe two. Additionally, computer 1100 may also have mass storage(removable 1112 and/or non-removable 1114) such as magnetic or opticaldisks or tape. Similarly, computer 1100 may also have input devices 1117such as user input device (FIG. 1, 104) and/or output devices 1116 suchas output device (FIG. 1, 190). Other aspects of device 1100 may includecommunication connections 1120 to other devices, computers, networks,servers, etc. using either wired or wireless media.

In one embodiment, to implement processes described herein computerreadable instructions that are stored on computer readable media areexecuted on a processor. Computer 1100 may include a variety of computerreadable media. Computer readable media can be any available media thatcan be accessed by computer 1100 and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer readable media may comprise computerstorage media and communication media. Computer storage media includesvolatile and nonvolatile, as well as removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to,random access memory (RAM), read only memory (ROM), EEPROM, flash memoryor other memory technology, CD-ROMs, digital versatile discs (DVDs) orother optical disc storage, magnetic cassettes, magnetic tapes, magneticdisc storage or other magnetic storage devices, or any other storagemedium which can be used to store the desired information and which canbe accessed by computer 910. Communication media typically embodiescomputer readable instructions, data structures, program modules orother transport mechanism and includes any information delivery media.The term “modulated data signal” means a signal that has one or more ofits characteristics set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as radio frequency andother wireless media. Combinations of any of the above are also includedwithin the scope of computer readable media.

It is to be appreciated and understood that the exemplary system of FIG.1 constitutes but one exemplary operating environment. Accordingly, thisdescription is not intended to limit application of the claimed subjectmatter to just this one type of operating environment. Rather, theprinciples described herein can be implemented in other similar ordifferent environments without departing from the spirit and scope ofthe claimed subject matter.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

We claim:
 1. A machine implemented method comprising the steps of:providing an interface for a designer to design a custom search engine;receiving the following information in the interface: a) either firstcontent to be searched or identification of first content to be searchedby the custom search engine; b) information that specifies how toconstruct a sub-query from first search results that are returned whenthe first content is searched by the custom search engine; c) eithersecond content to be searched or identification of second content to besearched using the sub-query, second search results are returned whenthe second content is searched using the sub-query; and d) informationthat specifies how to generate final search results from the firstsearch results and the second search results; storing the informationthat is received in the interface; and associating the storedinformation with the custom search engine.
 2. A machine implementedmethod as recited in claim 1, further comprising: receiving, in theinterface, information that specifies how the final search results areto be arranged in a search results page.
 3. A machine implemented methodas recited in claim 2, wherein the information that specifies how thefinal search results are to be arranged in a search results pagecomprises: information that specifies how to organize a combination ofinitial search results of the first content and additional searchresults of the second content.
 4. A machine implemented method asrecited in claim 3, wherein the information that specifies how toorganize a combination of initial search results of the first contentand additional search results of the second content comprises:information that specifies how to organize a repeating pattern of anitem from the initial search results with a corresponding item from thesecond content.
 5. A machine implemented method as recited in claim 1,further comprising: generating code for constructing a search box forentering an initial search query in a client that renders the searchbox, the code causes a framework for a search results page to beautomatically loaded in the client; and providing the code to thedesigner.
 6. A machine implemented method as recited in claim 1, furthercomprising: generating code to forwarding an initial search query to aserver that stores the information that is received in the interface andfor forwarding metadata that identifies the custom search engine; andproviding the code to the designer.
 7. A machine implemented method asrecited in claim 1, further comprising: receiving, in the interface, anindication of how to modify an initial search query prior to using theinitial search query to search the first content.
 8. A computer storagemedium having instructions, which when executed on a processor, causethe processor to: provide an interface that is configured to design acustom search engine; receive the following information in theinterface: a) either initial content to be searched or identification ofinitial content to be searched by the custom search engine; b)information that specifies how to construct sub-queries from ones ofinitial search results items that are returned when the initial contentis searched by the custom search engine; c) either additional content tobe searched or identification of additional content to be searched bythe custom search engine using the sub-queries; d) information thatspecifies how to generate final search results from the initial searchresults items and additional search result items based on using thesub-queries to search the additional content, wherein the final searchresults comprise an additional search result item corresponding to eachsub-query; and e) information that specifies how to arrange the finalsearch results in a search results page that comprises a repeatingpattern of an item from the initial search results items with acorresponding item from the additional content; store the informationthat is received in the interface; and associate the stored informationwith the custom search engine.
 9. A computer storage medium as recitedin claim 8, wherein the information that cause the processor to providean interface to design a custom search engine cause the processor to:present a layout page that allows the location of an item from theinitial search results items and the location of a corresponding itemfrom the additional search result items on the search results page to bespecified.
 10. A computer storage medium as recited in claim 8, whereinthe instructions further cause the processor to: generate code forconstructing a search box for entering an initial search query in aclient that renders the search box, the code causes a framework for asearch results page to be automatically loaded in the client; andprovide the code.
 11. A computer storage medium as recited in claim 8,wherein the instructions further cause the processor to: generate codeto forwarding an initial search query to a server that stores theinformation that is received in the interface and for forwardingmetadata that identifies the custom search engine; and provide the code.12. A computer storage medium as recited in claim 8, wherein theinstructions further cause the processor to: receive, from a requestor,an initial search query and metadata identifying the custom searchengine; identify the stored information based on the metadata; andreturn, to the requestor, final search results for the initial searchquery.
 13. A computer storage medium as recited in claim 8, wherein theinstructions further cause the processor to: receive, in the interface,an indication of how to modify an initial search query prior to usingthe initial search query to search the initial content.
 14. A systemcomprising a processor and a computer storage medium coupled to theprocessor, the computer storage medium having stored thereon a set ofinstructions, which when executed on the processor cause the processorto: provide an interface that is configured to allow a designer todesign a custom search engine; receive the following information in theinterface: a) either initial content to be searched or identification ofinitial content to be searched by the custom search engine; b)information that specifies how to construct sub-queries from initialsearch result items that are returned when the initial content issearched by the custom search engine; c) either additional content to besearched or identification of additional content to be searched by thecustom search engine using the sub-queries; d) information thatspecifies how to generate final search results from the initial searchresult items and additional search result items based on using thesub-queries to search the additional content, wherein the final searchresults comprise an additional search result item corresponding to onesof the initial search result items; and e) information that specifieshow to arrange the final search results in a search results page thatcomprises a repeating pattern of an item from the initial search resultsitems with a corresponding item from the additional content; store theinformation that is received in the interface; and associate the storedinformation with the custom search engine.
 15. A system as recited inclaim 14, wherein the information that cause the processor to provide aninterface for a designer to design a custom search engine cause theprocessor to: present a layout page that allows drag and drop of variouscomponents that defines how the search results page will be displayed.16. A system as recited in claim 14, wherein the information that causethe processor to provide an interface for a designer to design a customsearch engine cause the processor to: present a layout page that allowsthe location of an item from the initial search results and the locationof a corresponding item from the additional search result on the searchresults page to be specified.
 17. A system as recited in claim 14,wherein the instructions further cause the processor to: generate codefor constructing a search box for entering an initial search query in aclient that renders the search box, the code causes a framework for asearch results page to be automatically loaded in the client; andprovide the code to the designer.
 18. A system as recited in claim 14,wherein the instructions further cause the processor to: generate codeto forwarding an initial search query to a server that stores theinformation that is received in the interface and for forwardingmetadata that identifies the custom search engine; and provide the codeto the designer.
 19. A system as recited in claim 14, wherein theinstructions further cause the processor to: receive, from a requestor,an initial search query and metadata identifying the custom searchengine; identify the stored information based on the metadata; andreturn, to the requestor, final search results for the initial searchquery.
 20. A system as recited in claim 14, wherein the instructionsfurther cause the processor to: receive, in the interface, an indicationof how to modify an initial search query prior to using the initialsearch query to search the initial content.